Add Hydra searchpath for rf3 and rfd3 model-specific configs #166
+17
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Extends #144 by adding Hydra searchpath configuration for rf3 model configs, and completes the rfd3 implementation by adding missing searchpath entries to validate.yaml and dev.yaml.
Both rf3 and rfd3 configs are packaged as
rf3.configsandrfd3.configsrespectively (configured in pyproject.toml), but Hydra couldn't locate them without explicit searchpath entries.Changes:
pkg://rf3.configssearchpath to inference.yaml, train.yaml, and validate.yamlpkg://rfd3.configssearchpath to validate.yaml and dev.yaml (inference.yaml and train.yaml were already updated in previous commit)Both models now consistently use their model-specific configs package before falling back to shared
pkg://configs:💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.